APP05 Purpose:
APP05 processes emulate MESSAGING Subscriber firms by running on servers that are outside of access switches.
APP05 processes receive MESSAGING multicast from MESSAGING (APPGROUP1) processes.
APP05 Client applications allow users to view MESSAGING data statistics, status and error messaging as well as MESSAGING data.
Operations are the only users of MESSAGING Readers.
Any issue with MESSAGING Readers may, or may not, mean MESSAGING Subscribers are having similar issues.
See APPGROUP1 Application Specific Scenarios for information related to MESSAGING multicast.
Use the
following hyperlinks to jump to the desired section of APP05 documentation:
APP05_Monitoring_Considerations
APP05 Recovery
Considerations:
Stopping/Restart
Processes:
-
Use NTM Control Utility - Service Control -
Process Controller to stop/restart processes.
- APP05 processes do not move between data centers.
There are no APP05 related NTM Control Commands.
|
APP05 Symptom |
Impacts |
Response |
|
Node Crashes Evidenced by: - In Solarwinds (and outlook), node and processes will be reported down. |
MESSAGING Readers will not be able to receive MESSAGING multicast. Refer to: Server Recovery - MESSAGING
Reader.docx Server Specific Recoveries. |
1) Refer to: Server Recovery - MESSAGING Reader.docx Server Specific Recoveries. 2) Notify Management. |
APP05 Monitoring Considerations:
|
MESSAGING
Reader Client |
To Start: |
Key Indicators to
Monitor: |
Symptom: |
Response: |
|
Processes emulate MESSAGING Subscribers. MESSAGING Reader Client allows user monitoring of MESSAGING
Statistics, Messaging and MESSAGING data. |
PROD MENU: |
- Status Bar (bottom of client) - Backup State - Primary State - Messages Window |
Status Bar shows client in disconnected state. APPGROUP1 Process(es) are either down or Client started
before APPGROUP1 Processes. |
1) If APPGROUP1 processes are down, restart them. 3) If reconnection attempts fail, call Technical Services;
There may be networking issue. |
|
|
|
|
Backup State and/or Primary State is not “active”. APPGROUP1 multicast for alternate channel is not
subscribed to. |
1) Work with Tech Services to investigate potential
network issue. 2) If only one of the channels is not active, MESSAGING
Subscribers may not have an issue with the working channel. A Stop/Restart of the APPGROUP1 process
involved may correct the issue, understanding that this will interrupt MESSAGING
Subscribers reading the working channel, if there is one. |
|
|
|
|
Message Window shows APPGROUP1 related issues. |
See APPGROUP1 Application Recoveries. |